Skip to content

[no-release-notes] Release v0.57.2 - #3003

Closed
coffeegoddd wants to merge 1 commit into
mainfrom
cd-release
Closed

[no-release-notes] Release v0.57.2#3003
coffeegoddd wants to merge 1 commit into
mainfrom
cd-release

Conversation

@coffeegoddd

@coffeegoddd coffeegoddd commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

Created by the Release workflow to update DoltgreSQL's version

@coffeegoddd
coffeegoddd enabled auto-merge July 30, 2026 20:45
@github-actions

github-actions Bot commented Jul 30, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor
Main PR
covering_index_scan_postgres 1972.54/s 1923.37/s -2.5%
groupby_scan_postgres 129.15/s 130.53/s +1.0%
index_join_postgres 660.19/s 652.53/s -1.2%
index_join_scan_postgres 817.91/s 809.89/s -1.0%
index_scan_postgres 31.32/s 31.09/s -0.8%
oltp_delete_insert_postgres 747.52/s 694.89/s -7.1%
oltp_insert 657.97/s 645.20/s -2.0%
oltp_point_select 3306.79/s 3268.67/s -1.2%
oltp_read_only 3279.67/s 3238.77/s -1.3%
oltp_read_write 2383.77/s 2413.14/s +1.2%
oltp_update_index 688.97/s 701.63/s +1.8%
oltp_update_non_index 721.43/s 703.62/s -2.5%
oltp_write_only 1746.86/s 1689.49/s -3.3%
select_random_points 1993.68/s 1990.12/s -0.2%
select_random_ranges 1459.23/s 1490.39/s +2.1%
table_scan_postgres 30.51/s 30.66/s +0.4%
types_delete_insert_postgres 692.22/s 705.08/s +1.8%
types_table_scan_postgres 13.88/s 13.94/s +0.4%

@github-actions

github-actions Bot commented Jul 30, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor
Main PR
Total 42090 42090
Successful 18868 18867
Failures 23222 23223
Partial Successes1 5326 5326
Main PR
Successful 44.8278% 44.8254%
Failures 55.1722% 55.1746%

${\color{red}Regressions (1)}$

random

QUERY:          (SELECT unique1 AS random
  FROM onek ORDER BY random() LIMIT 1)
INTERSECT
(SELECT unique1 AS random
  FROM onek ORDER BY random() LIMIT 1)
INTERSECT
(SELECT unique1 AS random
  FROM onek ORDER BY random() LIMIT 1);
RECEIVED ERROR: expected row count 0 but received 1

Footnotes

  1. These are tests that we're marking as Successful, however they do not match the expected output in some way. This is due to small differences, such as different wording on the error messages, or the column names being incorrect while the data itself is correct. ↩

@fulghum fulghum closed this Aug 4, 2026
auto-merge was automatically disabled August 4, 2026 18:41

Pull request was closed

@itoqa

itoqa Bot commented Aug 4, 2026

Copy link
Copy Markdown

Ito QA test results
Commit: f4bc507: 9 test cases ran, 9 passed ✅.

Summary

Coverage focuses on release identity, startup and retry behavior, basic query availability, and consistency of data across fresh, restarted, disk-backed, in-memory, and upgraded environments. It includes both normal operation and recovery/upgrade scenarios, with healthy behavior observed throughout.

Safe to merge — the exercised startup, version-reporting, persistence, upgrade, and recovery behaviors all passed with no PR-attributable regressions or unresolved failures. No merge-blocking risk was identified.

Tests run by Ito

View full run

Result Severity Type Description
✅ — Release The built server artifact reports Doltgres version 0.57.3, and the clean server reports its PostgreSQL identity without retaining the old 0.57.1 value.
✅ — Release The new server opened data created by version 0.57.1 and returned the existing row after the upgrade. The earlier setup problem was resolved by using the published prior-release artifact, so no compatibility failure was found.
✅ — Release The upgraded server opened the older data directory, returned the saved row, and reported the current Doltgres release as 0.57.3 in the same session.
✅ — Runtime The running server's Dolt version function returned exactly 0.57.3.
✅ — Runtime The in-memory server started successfully, completed a query, and showed 0.57.3 for both the environment and SQL service.
✅ — Runtime The server restarted with the existing database intact. The saved row was still present, and the version query returned 0.57.3.
✅ — Runtime The disk-backed and in-memory servers both reported release 0.57.3 and accepted a basic query.
✅ — Startup A fresh server started with an empty data directory, created the default database, accepted the default login, and stayed available for later queries. A test row was written and read back successfully.
✅ — Startup The first startup stopped safely before opening a port. After the forced failure was removed, the server reused the same data directory, created the default database, accepted SQL queries, and kept one healthy listener.

Tip

Reply with @itoqa to send us feedback on this test run.

@coffeegoddd
coffeegoddd deleted the cd-release branch August 5, 2026 16:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@coffeegoddd @fulghum